Methods, Systems, and Apparatus for Email to Persistent Messaging

ABSTRACT

A chat-based persistent messaging platform that can seamlessly convert messages from different modalities (e.g., email clients and text message clients) into persistent messages and vice versa is described herein. The platform can include a parsing processor to convert messages into standard format data. A message classifier can process the standard format data into different subcomponents. These subcomponents can be translated into persistent messaging content via one or more content processing engines. The persistent messaging content can be converted into a persistent message via the parsing processor. The message classifier can also add messages into a persistent thread so that message history between two or more users can be maintained in perpetuity.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application a divisional of U.S. application Ser. No. 16/617,099,entitled “Methods, Systems, and Apparatus for Email to PersistentMessaging,” which was filed on Nov. 26, 2019, and which is a U.S.National Stage Application under 35 U.S.C § 371 of InternationalApplication No. PCT/US2019/061174, entitled “Methods, systems, andapparatus for email and/or text to persistent messaging,” which wasfiled on Nov. 13, 2019.

International application no. PCT/US2019/061174 claims the prioritybenefit, under 35 U.S.C. § 119(e), of U.S. Application No. 62/816,417,entitled “Methods, Systems, and Apparatus for Text to PersistentMessaging,” filed on Mar. 11, 2019, and of U.S. Application No.62/760,885, entitled “Methods, Systems, and Apparatus for Email toPersistent Messaging,” filed on Nov. 13, 2018.

Each of these applications are incorporated herein by reference in itsentirety.

BACKGROUND

As the world becomes more application-driven through the proliferationof general-purpose compute within desktop computers, laptop computers,mobile smartphones, tablets, and wearables, there has been anapplication explosion with the types of services provided by acollection of different unique and downloadable apps. In thecommunications space, there is email, Short Message Service (SMS),Multimedia Messaging Service (MMS), mobile messaging, instant messaging,team messaging, voice chat, voice calling, video calling, screensharing, and more. This explosion has led to a fragmentation in howpeople stay connected and how they communicate both personally andprofessionally. With this application explosion combined with legacyanalog and digital methods of communicating (e.g., plain old telephoneservice (POTS), radio, etc.), there is an overabundance of communicationmodalities competing for our time and attention. People are breakingaway from traditional standards and forming islands of non-standardcommunication, many times not offering or allowing a ubiquitous means ofconnecting and interacting with friends, family, and co-workers.

SUMMARY

Today with the power of public cloud technologies and the separation ofthe application layer from the network layer (e.g., Internet Protocol(IP) based communications and services that ride on top of broadbandnetwork services, also known as Over The Top (OTT)), persistentcommunications is becoming a new way for people to convergecommunication modalities to allow a combination of textual, vocal, andvisual communications into a single seamless conversationalcommunications and productivity experience.

Persistent messaging can combine email and messaging together into asingle ubiquitous experience. This can allow the 5.2 billion emailaddresses that originate over 281 billion emails per day to upgradetheir user experiences to a rich and immersive multimedia communicationsexperience that is available through modern consumer mobile and desktopdevices. The systems, apparatus, and methods disclosed herein canconnect the legacy email environment to a persistent messagingenvironment and can translate off-net email communications into on-netpersistent messaging communications and vice versa.

The problems with email today are numerous. Spam, malware, limitedattachment sizes, minimal support for embedded media (e.g., videoreal-time streaming), loss of time scale context, and more are makingemail more antiquated and less compatible with today's increasinglymobile world. With smart devices including high-definition color touchscreens, rich audio, interactive cameras, and hardware enhancements,along with high-speed broadband connections, there is an unmet need foran efficient and capable system that can deliver a modern messagingexperience that is well beyond email.

The problems with text messaging services today are also numerous.Limits to the number of characters a user can send per message, lack offile attachments, minimal support for embedded media (e.g., videoreal-time streaming), expensive international messaging rates, spam,malware, and more are making text messaging more antiquated and lesscompatible with the way people communicate today. With smart devicesincluding high-definition color touch screens, rich audio, interactivecameras, and hardware enhancements, along with high-speed broadbandconnections, there is an unmet need for an efficient and capable systemthat can deliver a modern messaging experience that is well beyond textmessaging.

The systems, apparatus, and methods disclosed herein modernize email byproviding a conversational threaded messaging user interface and cantranslate emails into a persistent messaging environment. In someembodiments, a conversational threaded messaging approach uses aconversational approach in which all messages between people and/orgroups are organized together. In some embodiments, the messages areorganized in a context dependent manner. The systems, apparatus, andmethods disclosed herein can include a translation engine that canparse, route, classify, process, and parse again to convert an emailinto a persistent message. The disclosed systems, apparatus, and methodscan also convert a persistent message into an email. This functionseamlessly allows the modern mobile environment to be forward andbackward compatible with the email market.

Similarly, the systems, apparatus, and methods disclosed herein canconnect legacy text messaging environment to a persistent messagingenvironment and can translate off-net text messaging communications intoon-net persistent messaging communications and vice versa.

A method for translating an email from a first user using an externalemail client into a persistent message to a second user using achat-based persistent messaging system is disclosed herein. The methodincludes receiving the email from the external email client at a receivequeue. The method also extracting at least one attribute associated withthe email and extracting standard format data from the email. The methodalso includes determining at a message router the next destination forthe standard format based on the at least one attribute. The nextdestination can include an on-net parsing processor and/or a messageclassifier. In response to determining that the next destination is themessage classifier, the standard format data is processed intosubcomponents representing content of the email at the messageclassifier. The method also includes adding the email to a persistentthread at the message classifier based on an historical interactionbetween the first user and the second user. The method also includestransmitting the subcomponents to respective content processing enginesfrom the message classifier, translating the subcomponents intopersistent messaging content at the respective corresponding contentprocessing engines, converting the persistent messaging content to apersistent message at the on-net parsing processor, and transmitting thepersistent message to the second user using the persistent messagingsystem.

In some instances, at least one attribute includes at least one of asender's email address, a sender's name, a recipient's email address, arecipient's name, date, time, email header information, or messagecontent included in the email.

In some instances, adding the email to persistent thread furtherincludes matching, at the message classifier, the standard format datafrom the email with the historical interaction between the first userand the second user based on the at least one attribute. The at leastone attribute can comprise the sender's email address and therecipient's email address. The persistent thread represents a priorhistorical interaction between the first user and the second user.

In some instances, adding the email to the persistent thread can furthercomprise determining, at the message classifier, existence of thehistorical interaction between the first user and the second user priorto adding the email to the persistent thread.

In some instances, the method can also include adding the content in theemail to a persistent database. In some instances, the method can alsoinclude disaggregating the standard format data based on the nextdestination for the standard format data.

A persistent messaging system for translating an email from a first userusing an external email client into a persistent message to a seconduser is disclosed herein. The system includes an off-net parsingprocessor to extract at least one attribute associated with the emailand standard format data from the email. The system also includes amessage router, communicatively coupled to the message router, todetermine a destination for the standard format data based on the atleast one attribute. The system also includes a message classifier,communicatively coupled to the message router, to process the standardformat data into subcomponents that represent content of the email, toadd the email to a persistent thread based on an historical interactionbetween the first user and the second user, and to transmit thesubcomponents to content processing engines that translate thesubcomponents into the persistent messaging content. The system alsoincludes an on-net parsing processor, communicatively coupled to themessage router, to convert the persistent messaging content into thepersistent message, and a user interface, communicatively coupled to theon-net parsing processor, to transmit the persistent message to thesecond user.

In some instances, the at least one attribute includes at least one of asender's email address, a sender's name, a recipient's email address, arecipient's name, date, time, email header information, or messagecontent included in the email. In some instances, the message classifieris further configured to match the standard format data from the emailwith the historical interaction between the first user and the seconduser based on the at least one attribute. The at least one attribute cancomprise the sender's email address and the recipient's email address.The message classifier can be further configured to determine anexistence of the historical interaction between the first user and thesecond user prior to adding the email to the persistent thread.

In some instances, the system further comprises a persistent database,communicatively coupled to the message classifier, to store thepersistent messaging content.

A method for translating a persistent message from a first user using apersistent messaging system to an email addressed to a second user usingan external email client is disclosed herein. The method includesreceiving the persistent message via a user interface. The method alsoincludes transforming the persistent message into standard format dataat a parsing processor. The method also includes determining a nextdestination for the standard format data at a message router. The nextdestination can be at least one of an off-net parsing processor or amessage classifier. In response to determining that the next destinationis a message classifier, the standard format data is processed at themessage classifier into subcomponents representing content of thepersistent message. The method also includes adding the persistentmessage to a persistent thread at the message classifier based onhistorical interaction between the first user and the second user. Themessage also includes transmitting the plurality of subcomponents fromthe message classifier to respective content processing engines. Themethod also includes translating the plurality of subcomponents to anemail content at the respective corresponding content processingengines. The method also includes converting the email content to anexternal client email at the off-net parsing processor. The externalclient email can be in a format that is compatible with the externalemail client. The method also includes transmitting the external clientemail to the second user via the external email client.

In some instances, adding the persistent message to the persistentthread further includes matching, at the message classifier, thestandard format data from the persistent message with the historicalinteraction between the first user and the second user based on at leastone attribute. The at least one attribute can comprise the sender'semail address and the recipient's email address. Adding the persistentmessage to the persistent thread can further comprise determining, atthe message classifier, an existence of the historical interactionbetween the first user and the second user prior to adding thepersistent message to the persistent thread.

In some instances, the method further comprises adding the content inthe persistent message to a persistent database. In some instances, themethod further comprises disaggregating the standard format data basedon the next destination for the standard format data.

A persistent messaging system to translate a persistent message from afirst user into an email addressed to a second user using an externalemail client is disclosed herein. The system includes a user interfaceto receive the persistent message. The system also includes an on-netparsing processor, communicatively coupled to the user interface, totransform the message into standard format data. The system alsoincludes a message router, communicatively coupled to the on-net parsingprocessor, to determine a next destination for the standard format data.The system also includes a message classifier, communicatively coupledto the message router, to add the persistent message to a persistentthread based on historical interaction between the first user and thesecond user, to process the standard format data into subcomponentsrepresenting content of the persistent message, and to transmit thesubcomponents to content processing engines that translate thesubcomponents into email content. The system also includes an off-netparsing processing, communicatively coupled to the message router, toconvert the email content to the email, the email being in a formatcompatible with the external email client. The system also includes asend queue, communicatively coupled to the off-net parsing processor, totransmit the email to the second user via the external email client.

In some instances, the message classifier can be further configured tomatch the standard format data from the persistent message with thehistorical interaction between the first user and the second user basedon at least one attribute. The at least one attribute can comprise thesender's email address and the recipient's email address. The messageclassifier can be further configured to determine an existence of thehistorical interaction between the first user and the second user priorto adding the persistent message to the persistent thread. In someinstances, the system further comprises a persistent database,communicatively coupled to the message classifier, to store thepersistent messaging content in the persistent message.

The systems, apparatus, and methods disclosed herein modernize textmessaging by using a conversational threaded messaging user interfacewhile translating SMS, MIMS, and other messaging systems into apersistent messaging environment. In some embodiments, a conversationalthreaded messaging approach uses a conversational approach in which allmessages between people and/or groups are organized together. In someembodiments, the messages are organized in a context dependent manner.The systems, apparatus, and methods disclosed herein can include atranslation engine that can parse, route, classify, process, and parseagain to convert a text message into a persistent message. The disclosedsystems, apparatus, and methods can also convert a persistent messageinto a text message.

A method for translating a text message from a first user using anexternal text client into a persistent message to a second user using achat-based persistent messaging system is disclosed herein. The methodincludes receiving the text message from the external text client at areceive queue. The method also includes at an off-net parsing processor,extracting at least one attribute associated with the text message andextracting standard format data from the text message. The method alsoincludes determining at a message router the next destination for thestandard format based on at least one attribute. The next destinationcan be at least one of the on-net parsing processors or a messageclassifier. The method also includes in response to determining that thenext destination is the message classifier, processing the standardformat data into subcomponents representing content of the text message.The method also includes adding the text message to a persistent threadat the message classifier based on a historical interaction between thefirst user and the second user. The method also includes transmittingthe subcomponents to respective content processing engines from themessage classifier, translating, at the respective content processingengines, the subcomponents into persistent messaging content, convertingthe persistent messaging content to a persistent message at the parsingprocessor, and transmitting the persistent message to the second userusing the persistent messaging system.

In some instances, adding the text message to a persistent threadfurther includes matching, at the message classifier, the standardformat data from the text message with the historical interactionbetween the first user and the second user based on at least oneattribute. The attribute can comprise the name and/or phone number ofthe first user (sender) and the name, phone number, and/or unique(numeric) ID of the second user (recipient). The system sends from aunique number (ID or phone number) and receives from that same uniquenumber to match the sent or received message from the recipient. Themethod can further include determining, at the message classifier,existence of the historical interaction between the first user and thesecond user prior to adding the text message to the persistent thread.

In some instances, the method can also include adding the content in thetext message to a persistent database. In some instances, the method canalso include disaggregating the standard format data based on the nextdestination for the standard format data. In some instances, the textmessage is a Short Message Service (SMS).

A persistent messaging system for translating a text message from afirst user using an external text client into a persistent message to asecond user is described herein. The system can include an off-netparsing processor to extract at least one attribute associated with thetext message and standard format data from the email. The system canalso include a message router, communicatively coupled to the messagerouter, to determine a destination for the standard format data based onthe at least one attribute. The system can also include a messageclassifier, communicatively coupled to the message router, to processthe standard format data into subcomponents that represent content ofthe text message, to add the text message to a persistent thread basedon an historical interaction between the first user and the second user,and to transmit the subcomponents to content processing engines thattranslate the subcomponents into the persistent messaging content. Thesystem can also include an on-net parsing processor, communicativelycoupled to the message router, to convert the persistent messagingcontent into the persistent message. The system can also include a userinterface, communicatively coupled to the on-net parsing processor, totransmit the persistent message to the second user.

In some instances, the message classifier can be further configured tomatch the standard format data from the text message with the historicalinteraction between the first user and the second user based on the atleast one attribute. The at least one attribute can comprise at leastone of a name of the first user, a phone number of the first user, aname of the second user, a phone number of the second user, or a uniquenumerical ID. The message classifier can be further configured todetermine an existence of the historical interaction between the firstuser and the second user prior to adding the text message to thepersistent thread.

In some instances, the system can further include a persistent database,communicatively coupled to the message classifier, to store thepersistent messaging content in the text message. In some instances, thetext message is a Short Message Service (SMS).

A method for translating a persistent message from a first user using achat-based persistent messaging system to a text message addressed to asecond user using an external text client is disclosed herein. Themethod includes receiving the persistent message via a user interface.The message also includes transforming the persistent message intostandard format data at an on-net parsing processor. The method alsoincludes determining a next destination for the standard format data ata message router. The next destination can be the off-net parsingprocessor, a message classifier, or both. The method also includes inresponse to determining that the next destination is the off-net parsingprocessor, processing the standard format data at the message classifierinto subcomponents representing content of the persistent message. Themethod also includes adding the persistent message to a persistentthread at the message classifier based on a historical interactionbetween the first user and the second user. The message also includestransmitting the subcomponents from the message classifier to respectivecontent processing engines. The method also includes translating thesubcomponents to a text message content at the respective correspondingcontent processing engines. The method also includes transmitting thetext message to the second user via the external text client.

In some instances, the method also includes transmitting the textmessage content from the respective content processing engines to theexternal email client via the message classifier and the message router.In some instances, adding the persistent message to the persistentthread further includes matching, at the message classifier, thestandard format data from the persistent message with the historicalinteraction between the first user and the second user based on at leastone attribute. The at least one attribute can comprise the sender'semail address and the recipient's phone number.

In some instances, adding the persistent message to the persistentthread can further include determining, at the message classifier, anexistence of the historical interaction between the first user and thesecond user prior to adding the persistent message to the persistentthread. In some instances, the method further includes adding thecontent in the persistent message to a persistent database. In someinstances, the method further includes disaggregating the standardformat data based on the next destination for the standard format data.

A persistent messaging system to translate a persistent message from afirst user into a text message addressed to a second user using anexternal text message client is described herein. The system includes auser interface to receive the persistent message. The system alsoincludes an on-net parsing processor, communicatively coupled to theuser interface, to transform the message into standard format data. Thesystem also includes a message router, communicatively coupled to theon-net parsing processor, to determine a next destination for thestandard format data. The system also includes a message classifier,communicatively coupled to the message router, to add the persistentmessage to a persistent thread based on historical interaction betweenthe first user and the second user, to process the standard format datainto subcomponents representing content of the persistent message, andto transmit the subcomponents to content processing engines thattranslate the subcomponents into text message content. The system alsoincludes an off-net parsing processing, communicatively coupled to themessage router, to convert the text message content to the text message,the text message being in a format compatible with the external textmessage client. The system also includes a send queue, communicativelycoupled to the off-net parsing processor, to transmit the text messageto the second user via the external text message client.

In some instances, the message classifier can be further configured tomatch the standard format data from the persistent message with thehistorical interaction between the first user and the second user basedon at least one attribute. The at least one attribute can comprise thesender's email address and the recipient's email address. The messageclassifier can be further configured to determine an existence of thehistorical interaction between the first user and the second user priorto adding the persistent message to the persistent thread.

In some instances, the system further includes a persistent database,communicatively coupled to the message classifier, to store thepersistent messaging content in the persistent message. In someinstances, the text message is a Short Message Service (SMS).

All combinations of the foregoing concepts and additional concepts arediscussed in greater detail below (provided such concepts are notmutually inconsistent) and are part of the inventive subject matterdisclosed herein. In particular, all combinations of claimed subjectmatter appearing at the end of this disclosure are part of the inventivesubject matter disclosed herein. The terminology used herein that alsomay appear in any disclosure incorporated by reference should beaccorded a meaning most consistent with the particular conceptsdisclosed herein.

BRIEF DESCRIPTIONS OF THE DRAWINGS

The skilled artisan will understand that the drawings primarily are forillustrative purposes and are not intended to limit the scope of theinventive subject matter described herein. The drawings are notnecessarily to scale; in some instances, various aspects of theinventive subject matter disclosed herein may be shown exaggerated orenlarged in the drawings to facilitate an understanding of differentfeatures. In the drawings, like reference characters generally refer tolike features (e.g., functionally similar and/or structurally similarelements).

FIG. 1 shows an example implementation of a platform for users toexchange emails and persistent messages.

FIG. 2 illustrates an example interface of the platform of FIG. 1 whenan email message is received from an off-net user addressed to an on-netuser.

FIG. 3 shows a flowchart illustrating a method of translating an emailmessage from an off-net user to a persistent message.

FIG. 4 illustrates an example interface of the platform of FIG. 1 when apersistent message is sent from an on-net user to an off-net email user.

FIG. 5 shows a flowchart illustrating the method of translating apersistent message from an on-net user to an email message.

FIG. 6 shows an example implementation of a platform for users toexchange text messages and persistent messages.

FIG. 7 illustrates an example interface of the platform of FIG. 6 when atext message is received from an off-net user addressed to an on-netuser.

FIG. 8 shows a flowchart illustrating a method of translating a textmessage from an off-net user to a persistent message.

FIG. 9 illustrates an example interface of the platform of FIG. 6 when apersistent message is sent from an on-net user to an off-net textmessage user.

FIG. 10 shows a flowchart illustrating a method of translating apersistent message from an on-net user to a text message.

DETAILED DESCRIPTION

The present disclosure describes concepts related to, andimplementations of, systems, apparatus, and methods for translatingemails to a persistent messaging environment and vice versa. The presentdisclosure also describes concepts related to, and implementations of,systems, apparatus, and methods for translating text messages to apersistent messaging environment and vice versa. In some implementation,the same systems, apparatus, and methods described herein can performboth—translating emails to a persistent messaging environment and viceversa as well as translating text messages to a persistent messagingenvironment and vice versa.

With the explosion of different communication modalities andapplications, communication between users has become fragmented. Usersrequire separate applications, accounts, and login credentials tointeract with friends, family, and co-workers. Each of theseapplications offer different user experiences. Users need to check eachof these different applications to keep up.

Traditional Communication Modalities

Email is one of the most popular forms of communication today. However,email suffers from various technological problems, including spam,malware, attachment size limitations, security issues, privacy issues,information overload, etc. In addition, emails do not enable real-timeinteraction. Emails are often slow, and it is easy to lose context sinceemail messages are not stored as conversational threads. Putdifferently, emails are often grouped by subject line, so differentemails between different users with a shared subject line are put undera single thread. Unfortunately, grouping/threading by subject does notnecessarily provide contextual information about prior interactions orrelations between two users. Worse, emails with the same subject linebut different subjects may be grouped in the same thread, which is whymany users turn off the grouping feature in Microsoft Outlook, Gmail,and other conventional email platforms.

Text messaging is another popular form of communication. Unfortunately,text messaging is limited in its capabilities. For instance, textmessages require two users communicating with each other to use acellular platform. Text messages also have character limits, are limitedin the types of media they support within the message, do not supporthyperlinked or embedded media, do not synchronize across user devices ortext clients, and do not work across different computing platformsincluding laptops, desktop computers, wearable devices, or other userinterfaces that have compute and network connectivity. Text messagesalso do not allow messages to be edited or deleted after they are sentand cannot be shared or forwarded to other users. In addition, textmessages have limited group capabilities and are typically designed forone-to-one type messaging interactions only. Text messages also do nottypically support the recipient's ability to react to a message; rather,they are limited to only a textual reply.

Persistent Messaging Environment

The systems, apparatus, and methods disclosed herein provide apersistent messaging environment or persistent messaging platform (alsoreferred to herein as “platform”) that includes a function to seamlesslyconvert messages from different communication modalities into persistentmessages and vice versa. A persistent message can converge communicationmodalities to allow a combination of textual, vocal, and visualcommunications into a single seamless conversational communication andproductivity experience. Rather than a transactional exchange betweentwo users with a defined start and end, a persistent messaging threadincludes exchanges between two users over a long period of time (e.g., apersistent message maintains these exchanges in perpetuity if desired).A persistent messaging thread enables contextual exchange between two ormore users and is not organized solely based on subject line, likeemail, or one-off communications, like text messages.

Advantages Over Traditional Email and Text Messaging

The ability to convert messages from different communication modalitiesinto persistent messages enables migration of different communicationmodalities into a single communication platform. Put differently, thepersistent messaging environment is platform-agnostic. That is, messagesfrom different communication modalities such as email, text, etc., canbe translated into a persistent message. The platform disclosed hereinenables users to switch from fragmented communications on differentcommunication modalities to a single consolidated communicationmodality. This is an advantage over email and text messaging, whichcannot be consolidated easily, if at all.

The platform disclosed herein provides a conversational interface thatis backwards compatible with the Email market and the text market. Putdifferently, when two or more users connect on the platform, it marksthe beginning of a persistent messaging thread. The persistent messagingthread (also referred to as a “messaging thread”) enables contextualexchange between two or more users. That is, related messages are storedas a single thread. The series of threaded messages between two or moreusers can include images, video, audio, etc. The message history can bemaintained in perpetuity. More specifically, the content in the messages(e.g., video content, audio content, image content, etc.) can be storedon a cloud platform and can be retrieved on demand at correspondingendpoints (i.e., delivered to respective users on their smartphone,desktop computers, or any other suitable computing device). This datacan be stored in encrypted and secure repositories and becomes theuser's data to retrieve, use, and/or exchange. In contrast, textmessages are saved locally on devices and are not maintained inperpetuity. Similarly, emails are often stored locally with a syncedhost on the cloud.

The platform disclosed herein makes it easier and faster to store andretrieve information. Based on the context, the users can access theappropriate messaging thread in order to retrieve information. Morespecifically, since messages from different communication modalities canbe stored on a single cloud platform, all the information from thedifferent communication modalities can be consolidated. This informationcan be retrieved and delivered to a corresponding endpoint at any timeby accessing the appropriate messaging thread. Some non-limitingexamples of endpoints include smartphones, tablets, smartwatches, laptopcomputers, desktop computers, etc. Put differently, information inmessaging threads associated with a user can be consolidated and madeavailable to the user on any computing device chosen by the user, makingit easier for the user to store and retrieve information.

The platform disclosed herein also provides several advantages over textmessaging. Unlike conventional text messaging, the platform disclosedherein does not have character limits. The platform also offers widesupport to different media types, cloud synchronization across alldevices and platforms, and continuous conversation with use ofpersistence. The platform disclosed herein also works across severalhardware devices such as desktop, laptop, wearable devices, and otheruser interfaces that have compute and network connectivity. The platformdisclosed herein can be used to edit and delete messages after they aresent. It can operate with fewer file size limitations and offersdelivery and read receipts. It can be used to react to a message withemojis, reply to and forward text messages, transition between email andtext messaging clients, and send hyperlinks and embedded media withinmessages.

The platform disclosed herein provides enhanced security compared toemail, text messaging, and other communication modalities. The systems,apparatus, and methods disclosed herein can include built-in encryptionsand/or blockchain(s) to authenticate and confirm authenticity of thecommunication as well as encryption to secure the content of thecommunications. The digital identity of users can be verified andvalidated across the blockchain. Blockchain specifically allows theuser's identity to be secure as well as portable and authenticatable asan original (for example, a digital identity can be verified forauthenticity based on an original blockchain sequence created at thetime the content was created).

For instance, if a first user sends an email message to a second userand the second user is connected to the persistent messaging platform,then the blockchain authenticates the digital identity (e.g., email id)of the first user. In this manner, the second user can be certain of theauthenticity of the email id (i.e., that the email id in fact belongs tothe first user) from which the second user gets the email. This makes iteasier to filter unwanted messages, including spam and phishing emails.The end-to-end encryption can be a key value proposition to scrutinizemessages. The off-net messages can be authenticated through blockchainhash.

The persistent messaging platform can create contacts in an intelligentmanner (also referred to herein as “smart contracts’). Once a usercreates a digital identity on the platform, the digital identity can beautomatically linked with the user's family, friends, coworkers, andcolleagues. If the user's connections have more than one digitalidentity (e.g., a first digital identity for personal and a seconddigital identity for work), the smart contacts can automaticallysynchronize these multiple digital identities into the appropriatecontact list. In some instances, a single digital identity of the usercan connect with all of the user's contacts. In some instances, the usercan create a separate digital identity to connect with a subset of theuser's contacts. The user can switch between all of the user's digitalidentities.

Conventionally, most people use basic contacts, each of which include aname, email, phone, address, etc. for another person. Each person storesthis basic contact information for these other people in a contacts listfor use at a later time. Conversely, an inventive smart contact is aprofile that each user creates for himself or herself. The smart contactincludes that person's contact information, relationships, education,likes/hobbies, and more, including social profile information. A usercan choose to share some or all of their smart contact info with theirconnections. Because each person maintains his or her own smart contact,instead of basic contact information for other people, the maintenanceburden is lower for each user. In addition, there is less chance that agiven user's contact information will become out-of-date, as a user'supdates to his or her own smart contact information (e.g., a new workemail address or phone number) automatically propagate to the user'sconnections.

The persistent messaging platform enhances privacy by providing theability to tailor the privacy settings for each digital identityelement. A digital identity element can include name, phone number,email id, relationships, and/or the like. For instance, if the singledigital identity has multiple digital identity elements (e.g. Name,Email, Phone, Address, Website, etc.), each of these elements can have adifferent privacy setting associated with it to allow or restrictsharing. In addition, each user can be given a key to lock theinformation and associated privacy settings in their correspondingcontact.

The persistent messaging platform enables portability of contacts. Oncea digital identity is created on the platform, the blockchaininterconnects thereby connecting the smart contacts. The blockchain withcloud-sync automatically updates the contact list for each user withoutthe necessity to do so manually.

The persistent messaging platform enables transmission of large files.Instead of sending attachments, the users that are registered on theplatform or users outside of the platform can send a link to the file.The file itself can be stored on a server in the system. The file storedon the server can be accessed by accessing a private or public link.Therefore, unlike emails, the platform disclosed herein is not limitedby attachment size limitations. For example, if a file is less than 10MB in size, the system may send the file directly to the recipient as ina normal email. If the size of the file is greater than 10 MB, thepersistent messaging platform can automatically send a link to the filestored on a cloud server instead of transmitting the file with themessage. Automatically replacing oversized files with links reducesbandwidth consumption and reduces the chance of an off-net serverrefusing a message because an attached file is too large while stillproviding the message and file to the intended recipient.

An off-net user is a user outside of the persistent messagingenvironment and an on-net user is a user inside of the persistentmessaging environment. An email client can be an external email clientsuch as Gmail®, Yahoo®, or Outlook®. A text messaging client accordingto some implementations of this disclosure can be an external textmessaging client available on an Android®, iPhone®, or Microsoft® orother mobile operating system (OS). A messaging thread is a series ofrelated messages in a contextual exchange between users. For instance,once an initial message is sent then all responses to the message can beincluded in a continuing messaging thread. Typically, a single messageis destined for either an individual thread or a group thread, but notboth.

Persistent messaging refers to a series of threaded messages betweenindividuals or groups where the content can include anything (e.g.,image, video, audio, GIFs, text, token, and/or the like) that can beexchanged digitally. Persistent messaging can also include a messagehistory which can be maintained in perpetuity if desired. Theinteraction between two or more individuals can use differentcommunication modalities (e.g., text, images, animations, emojis, motionvideo, etc.) that can all be consolidated into a singular contextualconversational interaction. A persistent messaging environment caninclude a complete on-net user experience including all usersparticipating in the persistent messaging environment. Email content canrefer to content within an email. An email can include the email contentand the message header. Text messaging content can refer to contentwithin an SMS, MMS, RCS, or other mobile messaging application. A textmessage can include messaging content including characters as well asimagery. Persistent message content can refer to the content portion ofa persistent message. The persistent message can include the content andadditional information needed to route and display the persistentmessage appropriately.

The systems, apparatus, and methods disclosed herein can provide aplatform for users to exchange emails, text messages and persistentmessages. In order to use the systems disclosed herein, certain usersmay be registered to use the platform and can participate as on-netusers. Other users may use communication modalities outside of theplatform and can participate as off-net users. Both on-net and off-netusers can exchange messages through the platform to exchange contentwithin the corresponding messages through their respective userinterfaces.

Email to Persistent Messaging

FIG. 1 is an example implementation of a platform for users to exchangeemails and persistent messages. In some implementations, the platform100 is a software platform that can be implemented on one or moreprocessors executing computer-readable instructions stored on associatedmemories. This platform 100 includes the following elements and/ormodules, each of which can be implemented on one or more processors. Insome implementations, a combination of one or more elements and/ormodules of platform 100 can be implemented on one or more processors.

Email Client 102

The Email client 102 can include a Post Office Protocol Version 3,Internet Message Access Protocol, Exchange, or other mail client that iscapable of sending and receiving emails. This can include an emailclient on a PC, smartphone, or tablet.

Receive Queue 106

The receive queue 106 can receive emails from an internet connection(e.g., Internet 104) and through an email service provider. Email thatis addressed to an on-net user in the persistent messaging environmentis first received at the receive queue 106 via Internet 104.

Send Queue 108

The send queue 108 can send emails from the persistent messagingenvironment to an email service provider via the Internet 104. Messagesthat are addressed to off-net email addresses are transmitted from thesend queue 108 via the Internet 104 to an email exchange.

Off-Net Parsing Processor 110

After an email has been received through the receive queue 106, theoff-net parsing processor 110 analyzes the content in the email anddisaggregates the content components into a standard format (e.g., JSON,XML, etc.). For example, basic Internet email format, such as describedin Request for Comments (RFC) 5532, can be parsed by the off-net parsingprocessor 110. The off-net parsing processor can parse and convert theRFC 5532 format into an email header and body with different tags. Thesetags can define fields such as priority, subject, etc. The off-netparsing processor 110 can convert the email into persistent messagestandard format which has a header and body with set of name/valuepairs. These tags are pre-defined for each message type. The emailmessage is converted into a persistent message with message type asemail and appropriate tags in the body.

The standardized content serves to create a predictable content data setfor the Content Processing Engines 120 (described below) to adapt andmodify for translation into persistent messaging interactions.

In some implementations, during conversion from persistent message to anemail, the off-net parsing processor 110 also receives data from themessage router 112 after it has been processed by the Content ProcessingEngines 120. This data is then assembled into an email and forwarded tothe Send Queue 108 for transmission to the Internet 104.

Message Router 112

The Message Router 112 receives data from the Off-net Parsing Processor110, the On-net Parsing Processor 114, and the Message Classifier 116 todetermine the next destination for the data.

If data is received from the Off-net Parsing Processor 110 or the On-NetParsing Processor 114, it typically is routed to the Message Classifier116 that then processes standard format data into its subcomponents.

If data is received from the Message Classifier 116, it is typicallyrouted to either the On-Net Parsing Processor 114 to be assembled into apersistent message or to the Off-Net Parsing Processor 110 to beassembled into an email depending upon where the data is intended to besent by the sender.

On-Net Parsing Processor 114

Once the on-net parsing processor 114 receives a persistent message fromthe persistent messaging user interface (e.g., web user interface 122 a,desktop user interface 122 b, smartphone user interface 122 c, tabletuser interface 122 d, wearables user interface 122 e, and/or the like),the on-net parsing processor 114 can analyze the content in thepersistent messages and can disaggregate the content components into astandard data format. The standard content form can serve to create apredictable content data set for the content processing engines 120 toadapt and modify for translation into email messages.

In some implementations, during conversion from an email to a persistentmessage, the on-net parsing processor 114 also receives data from themessage router 112 after standard form data has been processed androuted from the content processing engines 120. This data is thenassembled into a persistent message and forwarded to the persistentmessaging user interface for viewing by the persistent messaging client132, for example, persistent messaging client 132 a and persistentmessaging client 132 b.

Message Classifier 116

The message classifier 116 can process incoming and outgoing standardform data into its subcomponents and can separate the subcomponentparts. For instance, a message comprises header and a body. The headerdefines metadata elements. Metadata defines characteristics of themessage, such as type, possible formats such as video format orcharacter sets, such as UTF-8. The body can have several subcomponentsdepending on the message type defined in the header. For example,message type email can include recipient list, content, attachments, andsignatures. A meetup message type can include calendar components thatdefine date/time, time zone, location and invitee components, etc.

The message classifier 116 can transmit the subcomponent parts to theappropriate content processing engine 120. For instance, the messageclassifier 116 can detect the type of content (e.g., text, image, audio,video, etc.) in the subcomponent parts. This can include subcomponentcontent in textual, audio, or video form including providing servicesand handling for identification, ranking, blockchain processing,relationship analysis, spam filtering, transcription, malwaremitigation, and other content. Based on the detected content type, themessage classifier 116 transmits each subcomponent part to theappropriate content processing engine 120, which processes thesubcomponent part and returns it to the message classifier 116 formatching content.

The message classifier 116 can also match content received from both theemail client 102 and the persistent messaging client 132 to ensure acontiguous conversation from prior interactions that may have occurredbetween the two users. For instance, when an email message is convertedfrom standard email format (Internet Email message format as defined byRFC 5322)) into persistent message format, one or more identificationinformation in the email message such as email message id and/or replyto original message id can be used by the message classifier 116 tomatch content. The message classifier 116 can use the identificationinformation to identify if the email message should constitute a newthread or if it is a response to an existing persistent message. Thismatching of historical content maintained over time within thepersistent messaging database 118, ensures that interactions aremaintained between individuals or groups with context.

Persistent Database 118

The persistent database 118 contains a record of all interactions thathave occurred on the platform. This is a storage database with addressinformation, standard form data, content, and more that was exchangedbetween off-net and on-net as well as on-net to on-net users.

Content Processing Engines 120

The Content Processing Engines 120 transforms email content intopersistent messaging content and vice-a-versa. Each content processingengine 120 specializes in translation of content using techniquesdependent upon the type of content in need of translation services. Eachcontent processing engine 120 runs as an application within the cloudarchitecture.

Text Engine 121 a—processes and transforms textual related content toinclude any lexicon including symbols and other standard computercharacters. These include character languages from around the world.

Image Engine 121 b—processes and transforms visual related content toinclude still images as well as video related content. This can includeprocessing of images with additional filters, image editing (to includeresolution, color modification, etc.) or other image processingcapability that may be needed or requested by the platform and itsusers.

Files Engine 121 c—processes and transforms file related content toensure compatibility between the two environments. This can include fileprocessing, reformatting, compression, file conversion, and fileintegrity actions.

Blockchain Engine 121 d—processes any content that requires handling ofblockchain components to include verification, authentication,encryption, hashing, or other automated manipulation of content tosupport blockchain oriented services and features. The blockchain engine121 d can allow for portability and security of messages and/or contactsshared via the platform.

Relationship Engine 121 e—processes content that has a relationalcontext to it. This includes understanding personal, business, or entitydegrees of separation, data characteristics that offer insights orextrapolations about personal, business, or entity connections that mayexist, and other elements that drive better understanding about theconnections between parties

Spam AI Engine 121 f—seeks to identify, isolate, and mitigate possibleor actual spam content that is intended to solicit, threaten, or crowd auser's interaction experience. This engine acts upon spam to reduce andremove spam.

Transcription Engine 121 g—translates between spoken languages to allowa native speaker in one country to have their persistent messageconverted to another spoken language for either on-net or off-net usersand vice-a-versa. The transcription engine 121 g can receive spokenlanguage via emails or text messages that include audio or videorecordings. It can also receive spoken messages that come from thepersistent messaging client. The platform 100 may also support phonecalling, with incoming voicemails routed to the transcription engine 121g for processing the audio processed into text for display on thepersistent messaging client.

Malware Engine 121 h—seeks to identify, isolate, and mitigate possibleor actual threats including virus, malware, or phishing threats that maybe targeted to users in email and/or persistent messaging. This engineincludes industry standard, best practice, and proprietary technologiesto mitigate threats within communications and content.

User Interface 122

The user interface 122 enables an on-net user to consume and interactwith the content delivered from the on-net parsing processor 114. Theuser interface 122 also enables the on-net user to create and publishcontent to the on-net parsing processor 114 destined for either anotherpersistent messaging client 132 or destined for an email client 102.

Web User Interface 122 a—The web user interface 122 a provides contentin a resolution and delivery mechanism to be provided through any numberof modern computer web browsers including Google Chrome®, MozillaFirefox®, Microsoft Internet Explorer®, Microsoft Edge®, Safari®, orothers.

Desktop User Interface 122 b—The desktop user interface 122 b providescontent in a resolution and delivery mechanism available through adownloadable software application that can be installed and run on acomputer.

Smartphone User Interface 122 c—The smartphone user interface 122 cprovides content in a resolution and delivery mechanism availablethrough a downloadable software application to be installed on asmartphone including devices running Apple® iOS, Android OS, or othermobile operating systems.

Tablet User Interface 122 d—The tablet user interface 122 d providescontent in a resolution and delivery mechanism available through adownloadable software application to be installed on a tablet includingdevices running Apple® iOS, Android OS, or other mobile operatingsystems.

Wearable User Interface 122 e—The wearable user interface 122 e providescontent in a resolution and delivery mechanism available through adownloadable software application to be installed on a wearable deviceincluding devices running Apple® Watch OS, Android Wear OS, or otherwearable operating systems.

Other User Interface 122 f—The other user interface 122 f providescontent in a resolution and delivery mechanism available on any otherdevice or system that contains compute and network connectivity. Ascompute and network connectivity is introduced into more devices of alltypes, an installed software application can be provided to deliverpersistent messaging to these devices or services. For example, theother user interface 122 could be implemented in a car with a softwareapplication and display, such as a Tesla or Rivian, to deliverpersistent messaging.

Persistent Messaging Client 132

The persistent messaging client 132 allows a user to create, modify,view, or delete persistent message content in an interaction. Itprovides a graphical user interface that allows the user to use theservices, whether the persistent message content is delivered fromanother persistent messaging client 132 or from an email client 102.Persistent message content can include textual, vocal, or visualcommunications and content as well as other interactions that can besupported by the platform.

Translating Email to Persistent Message

FIG. 2 illustrates an example interface of the platform illustrating anemail that is sent from an off-net user to an on-net user. In thisexample, an off-net user 204 sends an email using an email client (e.g.,Gmail®) to an on-net user 202. The on-net user 202 responds to the emailusing the persistent messaging platform (e.g., response 206). Theoff-net user 204 receives the persistent message transformed as an emailon the email client. The off-net user 204 responds to the persistentmessage in the form of email which is once again transformed to apersistent message (e.g., message 208) that the on-net user 202 can readwith the persistent messaging platform. In this manner, the back andforth communication between the off-net user 204 and the on-net user 202can form a series of threaded messages. This thread can be maintained inperpetuity if desired.

FIG. 3 shows a flowchart illustrating a method of translating an emailmessage from an off-net user to a persistent message. At 302, an emailthat is sent from an email client (e.g., email client 102 in FIG. 1) canbe received at the receive queue (e.g., receive queue 106 in FIG. 1).The receive queue collects the email and ensures message integrity. Forexample, the receive queue can ensure message integrity based on theEmail Simple Mail Transfer Protocol (SMTP) standards for message receiptand acceptance. The email can then be forwarded to the off-net parsingprocessor (e.g., off-net parsing processor 110 in FIG. 1).

At 304, the off-net parsing processor can parse the email to obtainemail message content. For instance, the off-net parsing processor canparse the email to obtain the off-net user's email id, the name of theoff-net user, the on-net user's digital identity, the name of the on-netuser, users listed in the carbon copy field, users listed in the blindcarbon copy field, email header information, the included email messagecontent, and/or the like. The off-net parsing processor can also parsethe email message content into a standard data format and can pass thestandard data format to the message router (e.g., message router 112 inFIG. 1). The message router can determine the next destination for thestandard format data. For example, the message router determines thatthe standard format data should be transmitted to the message classifier(e.g., message classifier 116 in FIG. 1) and transmits the standardformat data to the message classifier.

At 306, the message classifier processes the standard format data intoits subcomponents and transmits the subcomponents to the relevantcontent processing engines (e.g., content processing engine 120 in FIG.1). At this point, the standard format data can be matched with thehistory of messages between the off-net user and on-net user to maintainhistorical context between the two parties. If no prior interactionhistory exists, a new persistent thread can be created.

At 308, the content processing engines translates the standard formatdata into persistent messaging content be it text, images, video, or anyother sort of multi-media. The standard format data can then betransmitted back to the message classifier to store the standard formatdata in the persistent database (e.g., persistent database 118 inFIG. 1) before transmitting the persistent message content to themessage router.

At 310, the message router transmits the persistent message content tothe on-net parsing processor (e.g., on-net parsing processor 114 inFIG. 1) which then generates the persistent message. At 312, thepersistent message can then be delivered to the user interface (e.g.,user interface 122) thereby initiating interaction from the persistentmessaging client (e.g., persistent messaging client 132 in FIG. 1).

Translating Persistent Message to Email

FIG. 4 illustrates an example interface of the platform when apersistent message is sent from an on-net user to an off-net email user.In this example, an on-net user 402 sends a persistent message 406 viathe platform 100 in FIG. 1 to an off-net user 404 using an email client(e.g., Gmail®). The platform 100 converts the persistent message 406 toan email and delivers the email to the off-net user 404 via the emailclient. The off-net user 404 can respond via the email client with anemail, which is transformed to persistent message (e.g., message 408)and delivered to the on-net user 402 using platform 100. As discussed inthe sections above, back and forth communication between the on-net user402 and off-net user 404 forms a series of threaded messages. Thisthread can be maintained in perpetuity if need be.

FIG. 5 shows a flowchart illustrating the method of translating apersistent message from an on-net user to an email message.

A persistent message can be sent from a persistent messaging client(e.g., persistent messaging client 132 in FIG. 1) through the persistentmessaging user interface (e.g., user interface 122 in FIG. 1). At 502,an on-net parsing processor (e.g., on-net parsing processor 114 inFIG. 1) collects the persistent message and parses the persistentmessage into a standard format. The standard format data is forwarded toa message router (e.g., message router 112 in FIG. 1). The messagerouter receives the standard format data and determines the nextdestination for where the standard format data should be handled. Forexample, the message router determines that the standard format datashould be transmitted to a message classifier (e.g., message classifier116 in FIG. 1) and does so.

At 504, the message classifier processes the standard format data intoits subcomponents (e.g., header and body) and transmits the standardformat data to relevant content processing engines (e.g., contentprocessing engine 120 in FIG. 1). At this point, the standard formatdata can be matched with the history of messages between the off-netuser and on-net user to maintain historical context between the twoparties. If no prior interaction history exists, the message classifiercreates a new persistent thread.

At 506, the content processing engines translates the standard formatdata into email content be it text, images, video, or any other sort ofmulti-media. The standard format data can then be transmitted back tothe message classifier to store the standard format data in thepersistent database (e.g., persistent database 118 in FIG. 1) beforetransmitting the email content to the message router.

At 508, the message router transmits the email content to the off-netparsing processor (e.g., off-net parsing processor 110 in FIG. 1) whichthen generates the email. At 510, the email can be transmitted to thesend queue (e.g., send queue 108 in FIG. 1), which then sends the emailfrom the persistent messaging environment to the internet connections.Messages that are addressed to off-net email addresses can betransmitted from the send queue to the internet mail exchange.

Text to Persistent Messaging

FIG. 6 is an example implementation of a platform for users to exchangetext messages and persistent messages. In some implementations, theplatform 600 is a software platform that can be implemented on one ormore processors executing instructions stored on associated memories.This platform 600 includes the following elements and/or modules, eachof which can be implemented on one or more processors. In someimplementations, a combination of one or more elements and/or modules ofplatform 600 can be implemented on one or more processors. Although, aseparate platform 600 from platform 100 is disclosed for users toexchange text messages and persistent messages, a single platform (e.g.,either platform 100 or platform 600) can be used to exchange textmessages and persistent messages as well as to exchange emails andpersistent messages.

Text Client 602

The Text client 602 can include a Short Message Service (SMS),Multimedia Messaging Service (MMS), or Rich Communication Service (RCS)application for sending and receiving text messages from other parties.This can include a text messaging client on a PC, smartphone, or tablet.

Receive Queue 606

The receive queue 606 can receive text messages from a networkconnection (e.g., Network 604) and through a text messaging serviceprovider. Text messages that are addressed to an on-net user in thepersistent messaging environment are first received at the receive queue606 via the Network 604.

Send Queue 608

The send queue 608 can send text messages from the persistent messagingenvironment to a text messaging service provider via the Network 604.Messages that are addressed to off-net text message phone numbers aretransmitted from the send queue 608 via the Network 604 to a textmessaging gateway connected to a text messaging service provider.

Off-Net Parsing Processor 610

After a text message has been received through the receive queue 606,the off-net parsing processor 610 analyzes the content in the textmessage and disaggregates the content components into a standard format(e.g., JSON, XML, etc.). For example, text messaging formats, such asdescribed in Request for Comments (RFC) 5724, can be parsed by theoff-net parsing processor 610. The off-net parsing processor can parseand convert the text messaging format of SMS, MIMS, and RCS into contentpieces with different tags. These tags can define fields such aspriority, subject, etc. The off-net parsing processor 610 can convertthe text message into persistent message standard format which has aheader and body with set of name/value pairs. These tags are pre-definedfor each message type. The text message is converted into a persistentmessage with message type as a text message and appropriate tags in thebody.

The standardized content serves to create a predictable content data setfor the Content Processing Engines 620 (described below) to adapt andmodify for translation into persistent messaging interactions.

In some implementations, during conversion from persistent message to atext, the off-net parsing processor 610 also receives data from themessage router 612 after it has been processed by the Content ProcessingEngines 620. This data is then assembled into an email and forwarded tothe Send Queue 608 for transmission to the Network 604.

Message Router 612

The Message Router 612 receives data from the Off-net Parsing Processor610, the On-net Parsing Processor 614, and the Message Classifier 616 todetermine the next destination for the data.

If data is received from the Off-net Parsing Processor 610 or the On-NetParsing Processor 614, it typically is routed to the Message Classifier616 that then processes standard format data into its subcomponents.

If data is received from the Message Classifier 616, it is typicallyrouted to either the On-net Parsing Processor 614 to be assembled into apersistent message or to the Off-net Parsing Processor 610 to beassembled into a text depending upon where the data is intended to besent by the sender.

On-Net Parsing Processor 614

Once the on-net parsing processor 614 receives the persistent messagefrom the persistent messaging user interface (e.g., web user interface622 a, desktop user interface 622 b, smartphone user interface 622 c,tablet user interface 622 d, wearables user interface 622 e, other userinterface 622 f, and/or the like), the on-net parsing processor 614 cananalyze the content in the persistent messages and can disaggregate thecontent components into a standard data format. The standard contentform can serve to create a predictable content data set for the contentprocessing engines 620 to adapt and modify for translation into textmessages.

In some implementations, during conversion from text to persistentmessage, the on-net parsing processor 614 also receives data from themessage router 612 after standard form data has been processed androuted from the content processing engines 620. This data is thenassembled into a persistent message and forwarded to the persistentmessaging user interface for viewing by the persistent messaging client632, for example, persistent messaging client 632 a and persistentmessaging client 632 b. If the text message is incompatible with thestandard form data, the text message can first be transformed into acompatible form and then converted from the compatible form intostandard format data.

Message Classifier 616

The message classifier 616 can process the standard form data into itssubcomponents and can separate the subcomponent parts. For instance, amessage comprises a header and a body. The header defines metadataelements. Metadata defines characteristics of the message, such as type,possible formats such as video format or character sets, such as UTF-8.The body can have several subcomponents depending on the message typedefined in the header. For example, message types can include recipientlist, content, attachments, and signatures. A meetup message type caninclude calendar components that define date/time, time zone, locationand invitee components, etc.

The message classifier 616 can transmit the subcomponent parts to theappropriate content processing engine 620. For instance, the messageclassifier 616 can detect the type of content (e.g., text, image, audio,video, etc.) in the subcomponent parts. This can include subcomponentcontent in textual, audio, or video form including providing servicesand handling for identification, ranking, blockchain processing,relationship analysis, spam filtering, transcription, malwaremitigation, and other content. Based on the detected type, the messageclassifier 616 can transmit the subcomponent parts to the appropriatecontent processing engine 620 for processing and return to the messageclassifier 616.

The message classifier 616 can also match content received from both thetext client 602 and the persistent messaging client 632 to ensure acontiguous conversation from prior interactions that may have occurredbetween the two users. For instance, when a text message is convertedfrom SMS, MIMS, or RCS format into a persistent message format, one ormore pieces of identification information in the text message such asthe phone number can be used by the message classifier 616 to matchcontent. The message classifier 616 can use the identificationinformation to identify if the text message should constitute a newthread or if it is a response to an existing persistent message. Thismatching of historical content maintained over time within thepersistent messaging database 618, ensures that interactions aremaintained between individuals or groups with context.

The message classifier 616 can match the content once the subcomponentparts have been processed by the appropriate content processing engine620.

Persistent Database 618

The persistent database 618 contains a record of all interactions thathave occurred on the platform. This is a storage database with addressinformation, standard form data, content, and more that was exchangedbetween off-net and on-net as well as on-net to on-net users.

Content Processing Engines 620

The Content Processing Engines 620 transforms text content intopersistent messaging content and vice-a-versa. Each content processingengine 620 specializes in translation of content using techniquesdependent upon the type of content in need of translation services. Eachcontent processing engine 620 runs as an application within the cloudarchitecture.

Text Engine 621 a—processes and transforms textual related content toinclude any lexicon including symbols and other standard computercharacters. These include character languages from around the world.

Image Engine 621 b—processes and transforms visual related content toinclude still images as well as video related content. This can includeprocessing of images with additional filters, image editing (to includeresolution, color modification, etc.) or other image processingcapability that may be needed or requested by the platform and itsusers.

Files Engine 621 c—processes and transforms file related content toensure compatibility between the two environments. This can include fileprocessing, reformatting, compression, file conversion, and fileintegrity actions.

Blockchain Engine 621 d—processes any content that requires handling ofblockchain components to include verification, authentication,encryption, hashing, or other automated manipulation of content tosupport blockchain oriented services and features. The blockchain engine121 d can allow for portability and security of messages and/or contactsshared via the platform.

Relationship Engine 621 e—processes content that has a relationalcontext to it. This includes understanding personal, business, or entitydegrees of separation, data characteristics that offer insights orextrapolations about personal, business, or entity connections that mayexist, and other elements that drive better understanding about theconnections between parties

Spam AI Engine 621 f—seeks to identify, isolate, and mitigate possibleor actual spam content that is intended to solicit, threaten, or crowd auser's interaction experience. This engine acts upon spam to reduce andremove spam.

Transcription Engine 621 g—translates between spoken languages to allowa native speaker in one country to have their persistent messageconverted to another spoken language for either on-net or off-net usersand vice-a-versa. In some implementations, the spoken language can bereceived by the platform 100 via an email or a text message thatincludes audio or video recording.

Malware Engine 621 h—seeks to identify, isolate, and mitigate possibleor actual threats including virus, malware, or phishing threats that maybe targeted to users in text messages and/or persistent messaging. Thisengine includes industry standard, best practice, and proprietarytechnologies to mitigate threats within communications and content.

User Interface 622

The user interface 622 enables an on-net user to consume and interactwith the content delivered from the on-net parsing processor 614. Theuser interface 622 also enables the on-net user to create and publishcontent to the on-net parsing processor 614 destined for either anotherpersistent messaging client 632 or destined for a text messaging client602.

Web User Interface 622 a—The web user interface 622 a provides contentin a resolution and delivery mechanism to be provided through any numberof modern computer web browsers including Google Chrome®, MozillaFirefox®, Microsoft Internet Explorer®, Microsoft Edge®, Safari®, orothers.

Desktop User Interface 622 b—The desktop user interface 622 b providescontent in a resolution and delivery mechanism available through adownloadable software application that can be installed and run on acomputer.

Smartphone User Interface 622 c—The smartphone user interface 622 cprovides content in a resolution and delivery mechanism availablethrough a downloadable software application to be installed on asmartphone including devices running Apple® iOS, Android OS, or othermobile operating systems.

Tablet User Interface 622 d—The tablet user interface 622 d providescontent in a resolution and delivery mechanism available through adownloadable software application to be installed on a tablet includingdevices running Apple® iOS, Android OS, or other mobile operatingsystems.

Wearable User Interface 622 e—The wearable user interface 622 e providescontent in a resolution and delivery mechanism available through adownloadable software application to be installed on a wearable deviceincluding devices running Apple® Watch OS, Android Wear OS, or otherwearable operating systems.

Other User Interface 622 f—The other user interface 622 f providescontent in a resolution and delivery mechanism available on any otherdevice or system that contains compute and network connectivity. Ascompute and network connectivity is introduced into more devices of alltypes, an installed software application can be provided to deliverpersistent messaging to these devices or services.

Persistent Messaging Client 632

The persistent messaging client 632 allows a user to create, modify,view, or delete persistent message content in an interaction. Itprovides a graphical user interface that allows the user to use theservices, whether the persistent message content is delivered fromanother persistent messaging client 632 or from a text client 602.Persistent message content can include textual, vocal, or visualcommunications and content as well as other interactions that can besupported by the platform.

Translating Text Message to Persistent Message

FIG. 7 illustrates an example interface of the platform when a textmessage is received from an off-net user addressed to an on-net user. Inthis example, an off-net user 704 sends a text message to an on-net user702. The platform transforms the text message into a persistent message706, which is visible to the on-net user 702 via the example interface(e.g., as message 706). The on-net user 702 then responds to the textmessage using the platform (e.g., response 708). The persistent messageis transformed to a text message and is delivered to the off-net user704. In this manner, the back and forth communication between theoff-net user 704 and the on-net user 702 can form a series of threadedmessages. This thread can be maintained in perpetuity if desired.

FIG. 8 shows a flowchart illustrating a method of translating a textmessage from an off-net user to a persistent message. At 802, a textmessage that is sent from a text messaging client (e.g., text client 602in FIG. 6) can be received at the receive queue (e.g., receive queue 606in FIG. 6). The receive queue collects the text message and ensuresmessage integrity. For example, the receive queue can ensure messageintegrity based on the SMS, MIMS, or RCS standards for message receiptand acceptance. The text message can then be forwarded to the off-netparsing processor (e.g., off-net parsing processor 610 in FIG. 6).

At 804, the off-net parsing processor parses the text message to obtaintext message content. For instance, the off-net parsing processor canparse the text message to obtain the off-net user's phone number, theon-net user's digital identity, the name of the on-net user, textmessage routing information, the included text message content, and/orthe like. The off-net parsing processor also parses the text messagecontent into a standard data format and passes the standard data formatto the message router (e.g., message router 612 in FIG. 6). The messagerouter determines the next destination for the standard format data. Forexample, the message router determines that the standard format datashould be transmitted to the message classifier (e.g., messageclassifier 616 in FIG. 6) and transmits the standard format data to themessage classifier.

At 806, the message classifier processes the standard format data intoits subcomponents and transmits the subcomponents to the relevantcontent processing engines (e.g., content processing engine 620 in FIG.6). At this point, the standard format data can be matched with thehistory of messages between the off-net user and on-net user to maintainhistorical context between the two parties. If no prior interactionhistory exists, a new persistent thread is created.

At 808, the content processing engines translates the standard formatdata into persistent messaging content be it text, images, video, or anyother sort of multi-media. The standard format data can then betransmitted back to the message classifier to store the standard formatdata in the persistent database (e.g., persistent database 618 in FIG.6) before transmitting the persistent message content to the messagerouter.

At 810, the message router transmits the persistent message content tothe on-net parsing processor (e.g., on-net parsing processor 614 in FIG.6) which then generates the persistent message. At 812, the persistentmessage is then delivered to the user interface (e.g., user interface622) thereby initiating interaction from the persistent messaging client(e.g., persistent messaging client 632 in FIG. 6).

Translating Persistent Message to Text Message

FIG. 9 illustrates an example interface of the platform when apersistent message is sent from an on-net user to an off-net textmessaging user. In this example, an on-net user 902 sends a persistentmessage 906 via the platform 600 of FIG. 6 to an off-net user 904. Theoff-net user 904 is using a text client. The persistent message 906 isconverted into a text message via the platform 600 and is delivered tothe off-net user 904 using the text client. As discussed above,back-and-forth communication between the on-net user 902 and off-netuser 904 forms a series of threaded messages. This thread can bemaintained in perpetuity if desired.

FIG. 10 shows a flowchart illustrating the method of translating apersistent message from an on-net user to a text message. A persistentmessage can be sent from a persistent messaging client (e.g., persistentmessaging client 632 in FIG. 6) through the persistent messaging userinterface (e.g., user interface 622 in FIG. 6). At 1002, an on-netparsing processor (e.g., on-net parsing processor 614 in FIG. 6)collects the persistent message and parses the persistent message into astandard format. The standard format data can be forwarded to a messagerouter (e.g., message router 612 in FIG. 6). The message router receivesthe standard format data and determines the next destination for wherethe standard format data should be handled. For example, the messagerouter determines that the standard format data should be transmitted toa message classifier (e.g., message classifier 616 in FIG. 6) and doesso.

At 1004, the message classifier processes the standard format data intoits subcomponents and transmits the standard format data to relevantcontent processing engines (e.g., content processing engine 620 in FIG.6). At this point, the standard format data can be matched with thehistory of messages between the off-net user and on-net user to maintainhistorical context between the two parties. If no prior interactionhistory exists, the message classifier creates a new persistent thread.

At 1006, the content processing engines translate the standard formatdata into text messaging content be it text, images, video, or any othersort of multi-media. The standard format data can then be transmittedback to the message classifier to store the standard format data in thepersistent database (e.g., persistent database 618 in FIG. 6) beforetransmitting the text messaging content to the message router.

At 1008, the message router transmits the text messaging content to theoff-net parsing processor (e.g., off-net parsing processor 610 in FIG.6) which then generates the text message. At 1010, the text message istransmitted to the send queue (e.g., send queue 608 in FIG. 6), whichthen sends the text message from the persistent messaging environment tothe internet connections. Messages that are addressed to off-net textmessaging users can be transmitted from the send queue to the network.

CONCLUSION

While various inventive embodiments have been described and illustratedherein, those of ordinary skill in the art will readily envision avariety of other means and/or structures for performing the functionand/or obtaining the results and/or one or more of the advantagesdescribed herein, and each of such variations and/or modifications isdeemed to be within the scope of the inventive embodiments describedherein. More generally, those skilled in the art will readily appreciatethat all parameters, dimensions, materials, and configurations describedherein are meant to be exemplary and that the actual parameters,dimensions, materials, and/or configurations will depend upon thespecific application or applications for which the inventive teachingsis/are used. Those skilled in the art will recognize or be able toascertain, using no more than routine experimentation, many equivalentsto the specific inventive embodiments described herein. It is,therefore, to be understood that the foregoing embodiments are presentedby way of example only and that, within the scope of the appended claimsand equivalents thereto, inventive embodiments may be practicedotherwise than as specifically described and claimed. Inventiveembodiments of the present disclosure are directed to each individualfeature, system, article, material, kit, and/or method described herein.In addition, any combination of two or more such features, systems,articles, materials, kits, and/or methods, if such features, systems,articles, materials, kits, and/or methods are not mutually inconsistent,is included within the inventive scope of the present disclosure.

Also, various inventive concepts may be embodied as one or more methods,of which an example has been provided. The acts performed as part of themethod may be ordered in any suitable way. Accordingly, embodiments maybe constructed in which acts are performed in an order different thanillustrated, which may include performing some acts simultaneously, eventhough shown as sequential acts in illustrative embodiments.

All definitions, as defined and used herein, should be understood tocontrol over dictionary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms.

The indefinite articles “a” and “an,” as used herein in thespecification and in the claims, unless clearly indicated to thecontrary, should be understood to mean “at least one.”

The phrase “and/or,” as used herein in the specification and in theclaims, should be understood to mean “either or both” of the elements soconjoined, i.e., elements that are conjunctively present in some casesand disjunctively present in other cases. Multiple elements listed with“and/or” should be construed in the same fashion, i.e., “one or more” ofthe elements so conjoined. Other elements may optionally be presentother than the elements specifically identified by the “and/or” clause,whether related or unrelated to those elements specifically identified.Thus, as a non-limiting example, a reference to “A and/or B”, when usedin conjunction with open-ended language such as “comprising” can refer,in one embodiment, to A only (optionally including elements other thanB); in another embodiment, to B only (optionally including elementsother than A); in yet another embodiment, to both A and B (optionallyincluding other elements); etc.

As used herein in the specification and in the claims, “or” should beunderstood to have the same meaning as “and/or” as defined above. Forexample, when separating items in a list, “or” or “and/or” shall beinterpreted as being inclusive, i.e., the inclusion of at least one, butalso including more than one, of a number or list of elements, and,optionally, additional unlisted items. Only terms clearly indicated tothe contrary, such as “only one of” or “exactly one of,” or, when usedin the claims, “consisting of,” will refer to the inclusion of exactlyone element of a number or list of elements. In general, the term “or”as used herein shall only be interpreted as indicating exclusivealternatives (i.e. “one or the other but not both”) when preceded byterms of exclusivity, such as “either,” “one of,” “only one of,” or“exactly one of.” “Consisting essentially of,” when used in the claims,shall have its ordinary meaning as used in the field of patent law.

As used herein in the specification and in the claims, the phrase “atleast one,” in reference to a list of one or more elements, should beunderstood to mean at least one element selected from any one or more ofthe elements in the list of elements, but not necessarily including atleast one of each and every element specifically listed within the listof elements and not excluding any combinations of elements in the listof elements. This definition also allows that elements may optionally bepresent other than the elements specifically identified within the listof elements to which the phrase “at least one” refers, whether relatedor unrelated to those elements specifically identified. Thus, as anon-limiting example, “at least one of A and B” (or, equivalently, “atleast one of A or B,” or, equivalently “at least one of A and/or B”) canrefer, in one embodiment, to at least one, optionally including morethan one, A, with no B present (and optionally including elements otherthan B); in another embodiment, to at least one, optionally includingmore than one, B, with no A present (and optionally including elementsother than A); in yet another embodiment, to at least one, optionallyincluding more than one, A, and at least one, optionally including morethan one, B (and optionally including other elements); etc.

In the claims, as well as in the specification above, all transitionalphrases such as “comprising,” “including,” “carrying,” “having,”“containing,” “involving,” “holding,” “composed of,” and the like are tobe understood to be open-ended, i.e., to mean including but not limitedto. Only the transitional phrases “consisting of” and “consistingessentially of” shall be closed or semi-closed transitional phrases,respectively, as set forth in the United States Patent Office Manual ofPatent Examining Procedures, Section 2111.03.

1. A method for translating a persistent message from a first user usinga persistent messaging system into an email to a second user using anexternal email client, the method comprising: receiving, via a userinterface, the persistent message from the first user to the seconduser; transforming, at an on-net parsing processor, the persistentmessage into standard format data, the standard format data including aheader and a body, the header comprising metadata defining individual ormultiple recipients, and the body comprising subcomponents representingthe content of the persistent message; determining, at a message router,a next destination for the standard format data based on at least oneattribute associated with the persistent message, the at least oneattribute comprising identifying information about the first user,identifying information about the second user, and the content of thepersistent message, the next destination being at least one of anoff-net parsing processor or a message classifier; in response todetermining that the next destination is the message classifier,matching, at the message classifier, the content of the persistentmessage from the standard format data with content of a persistentthread representing an historical interaction between the first user andthe second user or users based on the at least one attribute; adding thepersistent message to the persistent thread; storing the standard formatdata in a persistent database, the persistent database storing a recordof interactions between the first user and the second user on thepersistent messaging system; processing, at the message classifier, thestandard format data into subcomponents representing the content of thepersistent message; transmitting, from the message classifier, theplurality of subcomponents to respective content processing engines;translating, at the respective corresponding content processing engines,the plurality of subcomponents to email content, the email contentcomprising text, file-related content, and at least one of images,video, or multimedia; converting, at the off-net parsing processor, theemail content to the email, the email being in a format compatible withthe external email client; and transmitting, via a send queue, the emailto the second user via the external email client.
 2. The method of claim1, wherein the identifying information about the first user includes atleast one of a name of the first user or an email address of the firstuser and the identifying information about the second user includes atleast one of a name of the second user or an email address of the seconduser.
 3. The method of claim 1, wherein the persistent thread is a groupthread comprising content from a group of users including the first userand the second user.
 4. The method of claim 1, further comprising,before matching the content of the persistent message to the persistentthread: determining, at the message classifier, an existence of thehistorical interaction between the first user and the second user. 5.The method of claim 1, further comprising, before matching the contentof the persistent message to the persistent thread: creating thepersistent thread.
 6. The method of claim 1, further comprising:disaggregating the standard format data based on the next destinationfor the standard format data.
 7. The method of claim 1, furthercomprising: creating, by the first user, a smart contact includingcontact information and social profile information of the first user;and sharing, by the first user with the second user, information fromthe smart contact with the second user.
 8. The method of claim 7,further comprising: setting, by the first user, privacy settingsassociated with the smart contact.
 9. The method of claim 7, furthercomprising: automatically synchronizing multiple digital identities ofthe first user into a contact list of the smart contact.
 10. Apersistent messaging system for translating a persistent message from afirst user into an email to a second user using an external emailclient, the persistent messaging system comprising: a user interface toreceive the persistent message from the first user to the second user;an on-net parsing processor, operably coupled to the user interface, totransform the persistent message into standard format data, the standardformat data including a header and a body, the header comprisingmetadata defining individual or multiple recipients and the bodycomprising subcomponents representing the content of the persistentmessage; a message router, operably coupled to the on-net parsingprocessor, to determine a next destination for the standard format databased on at least one attribute associated with the persistent message,the at least one attribute comprising identifying information about thefirst user, identifying information about the second user, and thecontent of the persistent message; a message classifier, operablycoupler to the message router, to match the content of the persistentmessage from the standard format data with content of a persistentthread representing an historical interaction between the first user andthe second user or users based on the at least one attribute, to add thepersistent message to the persistent thread, to process the standardformat data into subcomponents representing the content of thepersistent message, and to store the standard format data in apersistent database, the persistent database storing a record ofinteractions between the first user and the second user on thepersistent messaging system; corresponding content processing engines,operably coupled to the message classifier, to translate the pluralityof subcomponents to email content, the email content comprising text,file-related content, and at least one of images, video, or multimedia;an off-net parsing processor, operably coupled to the content processingengines, to convert the email content to the email, the email being in aformat compatible with the external email client; and a send queue,operably coupled to the off-net parsing processor, to transmit the emailto the second user via the external email client.
 11. The persistentmessaging system of claim 10, wherein the identifying information aboutthe first user includes at least one of a name of the first user or anemail address of the first user and the identifying information aboutthe second user includes at least one of a name of the second user or anemail address of the second user.
 12. The persistent messaging system ofclaim 10, wherein the message classifier is configured to determine anexistence of the historical interaction between the first user and thesecond user.
 13. The persistent messaging system of claim 10, whereinthe persistent thread is a group thread comprising content from a groupof users including the first user and the second user.
 14. Thepersistent messaging system of claim 10, wherein the message classifieris configured to create the persistent thread.
 15. The persistentmessaging system of claim 10, wherein the on-net processor is configuredto disaggregate the standard format data based on the next destinationfor the standard format data.
 16. The persistent messaging system ofclaim 10, wherein the user interface is configured to enable to thefirst user to create a smart contact including contact information andsocial profile information of the first user and to share informationfrom the smart contact with the second user.
 17. The persistentmessaging system of claim 16, wherein the user interface is configuredto enable the first user to set privacy settings associated with thesmart contact.
 18. The persistent messaging system of claim 16, whereinthe smart contact is configured to automatically synchronize multipledigital identities of the first user.